feature: nympool contract #5464
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jstuczyn
force-pushed
the
feature/nympool-contract
branch
from
75e509c to
bdf3cd0
Compare
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
jstuczyn
changed the base branch from
develop
to
feature/cosmwasm2.2-upgrade
jstuczyn
force-pushed
the
feature/cosmwasm2.2-upgrade
branch
from
df9dec7 to
c95f815
Compare
jstuczyn
force-pushed
the
feature/nympool-contract
branch
from
badaafb to
0e0c520
Compare
jstuczyn
force-pushed
the
feature/cosmwasm2.2-upgrade
branch
from
c95f815 to
ebedcfa
Compare
jstuczyn
force-pushed
the
feature/nympool-contract
branch
from
3ab1a0a to
5063bc5
Compare
jstuczyn
force-pushed
the
feature/cosmwasm2.2-upgrade
branch
2 times, most recently
from
4ab3efb to
2e27dfd
Compare
|
this branch needs rebasing as |
initialised nym-pool contract and updated all bls12_381 to make it possible create scaffolding for tests ability to control the contract admin introducing contract grants grant type validation basic grant operations + stubs for other messages added queries use transaction stubs added expiration information to grant queries setting initial grant state based on the current environment allowance logic for attempting to spend part of a grant implemented all remaining transactions made public api for coin locking perform validation tests for locked tokens storage nympool storage tests added messages for changing granter set tests and fixes for sufficient tokens when inserting grants tests for initial state + more bugfixes queries tests additional tests for transactions and fixes post rebase fixes updated contract dependencies removed redundant wasm constructor dont ask me why this suddenly became an issue - no clue removed redundant wasm constructor dont ask me why this suddenly became an issue - no clue
jstuczyn
force-pushed
the
feature/nympool-contract
branch
from
5063bc5 to
cd230f6
Compare
jstuczyn
force-pushed
the
feature/nympool-contract
branch
from
a4b678e to
cc52be2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is the first iteration of the nympool contract. It's currently not yet integrated with the mixnet contract. However, given I have shifted my focus elsewhere, I'd rather get it merged in its current form to prevent the further code rot.
You can read more about the design ideas behind the contract in confluence
This change is